Before You Package Your Licensed Application

Before you package your licensed application, you should note the following points:

Modify the application installer

You will need to modify the installer for your application to include the customer-related files. The files you ship differ slightly depending on whether your application is configured for standalone or network operation, or both.

Choose appropriate utilities for your customers

•Under the Sentinel RMS installation structure in Windows, the..\Redistributable\Tools sub-directory contains a suggested directory structure for the files you ship to your customers. Within that structure, most of the files that you need to ship to your customer are available. From this master set of files, you will select the files to ship.

•In UNIX and Linux ARM, the .../redistributable/tools directory contains all the utilities. These are not segregated for various categories of users such as the system administrator, end user and so on.

•The table Miscellaneous Utilities in Chapter - Sentinel RMS Components provides a summary of all the RMS utilities. Apart from the utilities discussed above in the table, there are the decode utilities (lsdecode and ulsdcod). These utilities display the decrypted license information, and are recommended to be shipped to your customers under necessary circumstances only.

•You must send the appropriate licensing library (standalone, network, or integrated) with the utilities. Without the correct library, these utilities will not run. The libraries may not be required if your licensed application is statically linked with the Sentinel RMS libraries. You need to ship the libraries only when dynamic linking is used.

Digitally sign your binaries

Sentinel RMS licensed applications and License Manager store licensing data on end user’s machines. However, security software and anti-virus programs sometimes restrict Sentinel RMS components from reading and modification of licensing data. To prevent this, you must consider the following measures:

>Digitally sign your binaries to confirm that the information originated from the signer and has not been altered and hence enhance the credibility of the licensed application on the end user's machines.

>Whitelist the persistence path in your implementation. To learn more about the specific locations of the persistence files, contact Technical Support.